fix: use observation_time for forecast datetime field#71
Merged
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
null8626
approved these changes
May 20, 2026
Owner
null8626
left a comment
null8626
left a comment
There was a problem hiding this comment.
Hey, thank you so much for this pull request! ❤️ Apologies for the three-day delay, as this pull request appeared when I was in the middle of my final exams. Will publish a new release carrying this patch! ❤️
null8626
added a commit
that referenced
this pull request
May 20, 2026
Owner
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
localObsDateTimefield seems to have been removed from the wttr.in JSON response as a KeyError is currently being raised every timeClient.getis called. Fixed using thecurrent_timefield instead, and assuming the date to be today's date.